Creating an Omni Tactic

Omni Tactics utilize functionality that allows integration with the Pentaho Kettle ETL tool. An Omni Tactic can trigger actions, commands or processing implemented by the Pentaho Kettle tool.

When the file portion of the Tactic fires, Campaign Manager creates a file in a configured FTP site. The Campaign processor then calls the Pentaho Kettle job configured as part of the Omni Tactic. For example, use Pentaho Kettle scripts to change delimiters or qualifiers for richer output options, or to call a script within Pentaho Kettle that interacts with JavaScripts to deploy directly to the Twitter API.

The basic process is that the file portion of the Tactic will fire and create a file in a configured location, and the Campaign system then calls the Pentaho Kettle job configured as part of the Omni Tactic.

For more information on Configuring an Omni Tactic, refer to the External Agents section of the Campaign Manager Administration Guide.

Procedure

1. Click the drop-down arrow in the Select One field.

A list of file channels are now displayed. For example:

2. Select the channel type.
3. Click Add.
4. Enter the Creative name. Creative is a mandatory field, and therefore the Campaign cannot be processed without it. If the creative name is not visible on your screen click the button to move the tactic and its tabs upwards on the screen. Channel Type refers to the channel used and cannot be amended
5. In the Creative tab:
   1. Select the Creative definition (the name of your External Agent, linked to a Kettle script). The name given here is the given name for the Pentaho Kettle script and will only appear if configured in the script.

   

   2. The Creative parameters are then populated by the parameters set up in your Kettle Script. They allow users to interact with values in the Pentaho Kettle script and will only appear here if configured to do so.

   

   3. Rename the parameter Values, if required, for the tactic by clicking in the relevant value. If you want the names to be permanently changed then this will need to be done either in the kettle script or via External Agents in Settings.

   If you change your Creative definition, click on Refresh Agent for the Creative Parameters to be updated.

6. In the Fields tab:
   1. Map to columns in the database or defined as variables, to map to those columns required by the Pentaho Kettle scripts. The fields on this tab are the fields specified within the Pentaho Kettle script. For example:

   

   2. Click in the relevant field to amend the Type, Width, and Value.
   3. Click Save fields in a Layout Template to save the fields brought through from the Kettle script in a Layout Template.
7. In the Events tab, use the Import Events tool to import events and/or the When in Segment tool to log campaign events based on filters that have been set up to capture responses.

For example, when a recipient enters a defined segment by purchasing a particular product, or have arrived on a landing page by clicking a link in an email, and the Response Attribution tool to monitor the success of a specific campaign and creative, for example seeing how many orders were placed as part of the campaign.

8. In the Seeds tab, send campaigns as a test, for example to your marketing department to see whether the campaign reaches its target audience without it affecting your message send count.

The seeds file needs to be imported from the document explorer in either .csv or .txt file format. The seeds file needs to contain headers that map to the values in the Fields tab. Unless these values are mapped then the seeds cannot be sent. Note that any date fields used must be in a format recognized by Engine.

• Omni Tactics
  • Creating an Omni Tactic